Cloud based mobile device security and policy enforcement

ABSTRACT

Cloud based mobile device security and policy systems and methods use the “cloud” to pervasively enforce security and policy on mobile devices. The cloud based mobile device security and policy systems and methods provide uniformity in securing mobile devices for small to large organizations. The cloud based mobile device security and policy systems and methods may enforce one or more policies for users wherever and whenever the users are connected across a plurality of different devices including mobile devices. This solution ensures protection across different types, brands, operating systems, etc. for smartphones, tablets, netbooks, mobile computers, and the like.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of co-pending U.S. patent applicationSer. No. 13/243,807 filed Sep. 23, 2011, and entitled “CLOUD BASEDMOBILE DEVICE SECURITY AND POLICY ENFORCEMENT,” which is acontinuation-in-part of U.S. patent application Ser. No. 13/206,337filed Aug. 9, 2011 (now U.S. Pat. No. 9,060,239 which issued on Jun. 16,2015), and entitled “CLOUD BASED MOBILE DEVICE MANAGEMENT SYSTEMS ANDMETHODS,” and this application is a continuation-in-part of co-pendingU.S. patent application Ser. No. 13/051,519 filed Mar. 18, 2011 (nowU.S. Pat. No. 8,763,071 which issued Jun. 24, 2014), and entitled“SYSTEMS AND METHODS FOR MOBILE APPLICATION SECURITY CLASSIFICATION ANDENFORCEMENT,” the contents of each are incorporated in full by referenceherein.

FIELD OF THE INVENTION

The present invention generally relates to mobile device systems andmethods. More particularly, the present invention relates to cloud basedmobile device security and policy systems and methods to use the “cloud”to enforce pervasively security and policy on mobile devices.

BACKGROUND OF THE INVENTION

The adoption of smart mobile devices such as smartphones, tablets, etc.by consumers and enterprises is occurring at a staggering rate. It isestimated that such devices will shortly eclipse the annual shipments ofdesktop and laptop computers. Employees frequently bring mobile devicesinto work, i.e. in the enterprise. With the proliferation of mobiledevices in the enterprise, Information Technology (IT) administratorscan no longer ignore these devices as outside their scope ofresponsibility. In fact, mobile devices are now as powerful as laptopcomputers. Employees want to access corporate data and the Internetthrough wireless networks such as Wi-Fi hotspots (IEEE 802.11 andvariants thereof) or cellular data networks (e.g., 3G/4G, WiMax, etc.)which are outside the control of IT. On mobile devices, the line betweenenterprise and personal usage is blurred. Since the enterprise typicallydoes not own the device, enforcing policies for acceptable usage orinstalling application controls as a traditional IT administrator wouldon a corporate PC, is often not viable.

Conventionally, security vendors have responded to emerging mobilethreats by extending the desktop antivirus concept to mobile devices inthe form of “security apps”. Unlike the personal computer (PC) world,which is dominated by Microsoft, there are several different mobileoperating systems such as systems from Apple, Android, Windows Mobile,Blackberry, Symbian, Palm/HP, etc. Each platform has its own softwaredevelopment environment and a security vendor developing mobile securityapps has to replicate the effort across various platforms. Furthermore,some platforms such as Apple iOS do not allow traditional antivirus appson their devices. Loading third-party apps not approved by the platformvendor may lead to violation of the contract and often requiresjailbreaking the device which is definitely not an enterprise option.Even if security apps are allowed, they are a headache to deploy,require constant updates and are easy to circumvent, i.e. the user cansimply uninstall them if they are disliked. Worst of all, the securityapps impact device performance and degrade the user experience bystretching the already limited processor, memory, and battery resourceson the mobile device.

BRIEF SUMMARY OF THE INVENTION

In an exemplary embodiment, a mobile device security and policyenforcement method implemented by a node in a cloud based systemincludes, subsequent to communicatively coupling a mobile device to thenode, monitoring data between the mobile device and an external network;performing one or more of (i) enforcing policy relative to the data,wherein the policy is associated with a user of the mobile device and(ii) inspecting the data for malicious content therein; allowing thedata responsive to the data complying with the policy and/or containingno malicious content; and blocking the data in the node responsive toone or more of the data not complying with the policy and containingmalicious content. The monitoring, the enforcing, the inspecting, theallowing, and the blocking can be performed by the node without aplatform-specific app on the mobile device. The malicious content caninclude one or more of viruses, spyware, malware, Trojans, botnets, spamemail, phishing content, and blacklisted content. The policy can includeone or more of inappropriate content, data leakage, data usage limits,time-of-day usage limits, location, operation of a particularapplication, and black lists of websites. The policy can includepreventing installation of a particular application on the mobiledevice. The particular application can be blocked for one or more offailing to meet a minimum threshold for security and/or privacy andinterfering with an enterprise network associated with the user. Themobile device security and policy enforcement method can further includereceiving an update to the policy for the user or for a group of userscomprising the users; and performing the enforcing with the updatedpolicy. The mobile device security and policy enforcement method canfurther include receiving an update related to the malicious contentfrom another node in the cloud based system; and performing theinspecting the data with the update. The node can form an associationwith the mobile device.

In another exemplary embodiment, a mobile device security and policyenforcement system includes a network interface communicatively coupledto a processor; and memory storing instructions that, when executed,cause the processor to: subsequent to communicatively coupling to amobile device, monitor data between the mobile device and an externalnetwork; perform one or more of (i) enforce policy relative to the data,wherein the policy is associated with a user of the mobile device, and(ii) inspect the data for malicious content therein; allow the dataresponsive to the data complying with the policy and/or containing nomalicious content; and block the data in the node responsive to one ormore of the data not complying with the policy and containing maliciouscontent.

In a further exemplary embodiment, a mobile device includes a networkinterface communicatively coupled to a processor; and memory storinginstructions that, when executed, cause the processor to, subsequent tocommunicatively coupling to a node in a mobile device security andpolicy enforcement system, transmit data to an external network throughthe node, wherein responsive to the data one or more of (i) complyingwith policy associated with a user of the mobile device based onenforcement by the node and (ii) containing no malicious data thereinbased on inspection by the node, the node is configured to allow thedata; responsive to responsive data from the external network one ormore of (i) complying with the policy based on enforcement by the nodeand (ii) containing no malicious content therein based on inspection bythe node, receive the responsive data, from the node; and responsive toany of the data not complying with the policy, responsive to the datacontaining malicious data therein, responsive to the responsive datafrom the external network not complying with the policy, or responsiveto the responsive data containing malicious content therein, receive anotification from the node.

In an exemplary embodiment, a cloud based security method for a mobiledevice includes providing a mobile configuration to the mobile device,the mobile configuration configured to provide communications betweenthe mobile device and external network through a cloud based system;receiving communications from the mobile device for the externalnetwork; analyzing the communications from the mobile device for policyand security compliance therewith; and blocking the communications fromthe mobile device based on a violation of the policy and securitycompliance. In another exemplary embodiment, a mobile device includes anetwork interface configured to connect to a wireless network; memory;and a processor, the network interface, the memory, and the processorare communicatively coupled therebetween; wherein the processor with thenetwork interface and the memory is configured to: connect to a cloudbased security system over the wireless network; communicate data withan external network through the cloud based security system; and receivenotifications of content blocking of the data from the cloud basedsecurity system based on security and policy violations. In yet anotherexemplary embodiment, a cloud network configured to perform mobiledevice security and policy enforcement includes a plurality of cloudnodes communicatively coupled to a network, each of the plurality ofcloud nodes is configured to: communicate with a mobile device; andperform mobile device policy and security enforcement of the mobiledevice while concurrently providing access to the network.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated and described herein with referenceto the various drawings of exemplary embodiments, in which likereference numbers denote like method steps and/or system components,respectively, and in which:

FIG. 1 is a network diagram of a distributed security system which maybe utilized for mobile device security and policy enforcement;

FIG. 2 is a network diagram of the distributed security system of FIG. 1illustrating various components in more detail;

FIG. 3 is a block diagram of a server which may be used in thedistributed security system of FIG. 1 or standalone

FIG. 4 is a block diagram of a mobile device which may be used in thesystem of FIG. 1 or with any other cloud-based system;

FIG. 5 is a network diagram of a cloud system for implementing cloudbased mobile device management (MDM) and mobile device security andpolicy enforcement;

FIG. 6 is a flowchart and a network diagram of an Exchange ActiveSyncprovisioning method for the cloud system of FIG. 5 or the distributedsecurity system of FIG. 1;

FIG. 7 is a flowchart and a network diagram of another ExchangeActiveSync provisioning method for the cloud system of FIG. 5 or thedistributed security system of FIG. 1;

FIG. 8 is a flowchart and a network diagram illustrate a platformspecific MDM configuration for the cloud system of FIG. 5 or thedistributed security system of FIG. 1;

FIGS. 9-14 are graphical user interfaces (GUI) illustrate screen shotsof an MDM provisioning platform associated with the cloud system of FIG.5 or the distributed security system of FIG. 1;

FIGS. 15 and 16 are GUIs of screen shots of reporting and graphingassociated with the cloud based MDM system and method;

FIGS. 17A and 17B are network diagrams of a network of an exemplaryimplementation with one or more mobile devices communicatively coupledto an external network via a distributed security system, a cloudsystem, or the like;

FIG. 18 is a flowchart of a mobile device use method for using acloud-based security system with a mobile device;

FIG. 19 is a flowchart of a mobile application classification method forclassifying applications associated with mobile devices;

FIG. 20 is a flowchart of a mobile device security method using acloud-based security system with a mobile device.

FIG. 21 is a flowchart and screen shots of an exemplary operation ofIPsec VPN with cloud based mobile device security and policy systems andmethods;

FIG. 22 is a flowchart and screen shots of an exemplary operation ofJunos Pulse Secure Socket Layer (SSL) with cloud based mobile devicesecurity and policy systems and methods.

FIGS. 23-26 are GUI screen shots of security and policy enforcement inthe cloud on a mobile device; and

FIG. 27 is a GUI screen shot of a user interface for a networkadministrator of a cloud based security system.

DETAILED DESCRIPTION OF THE INVENTION

In various exemplary embodiments, the present invention relates to cloudbased mobile device security and policy systems and methods to use the“cloud” to enforce pervasively security and policy on mobile devices.The cloud based mobile device security and policy systems and methodsprovide uniformity in securing mobile devices for small to largeorganizations. The cloud based mobile device security and policy systemsand methods may enforce one or more policies for users wherever andwhenever the users are connected across a plurality of different devicesincluding mobile devices. This solution ensures protection acrossdifferent types, brands, operating systems, etc. for smartphones,tablets, netbooks, mobile computers, and the like.

Additionally, cloud based mobile device management (MDM) systems andmethods may use the “cloud” to manage pervasively mobile devices. Thecloud based MDM systems and methods provide an ability to manage mobiledevices with or without MDM clients while not requiring an MDM applianceor service at the enterprise. This provides a “no hardware, no software”deployment. In an exemplary embodiment, a client-less implementationleverages the ActiveSync protocol proxied through distributed cloudnodes to enforce mobile policies. In another exemplary embodiment, aclient-based implementation uses a platform specific application andassociated application programming interfaces (API) to connect managedmobile devices to any one of several distributed nodes in the cloud andprovide MDM features through the cloud. Advantageously, the cloud basedMDM systems and methods provide reliability and resiliency, elasticity,lower cost, mobility, integration of management and security, andagility over conventional MDM based solutions.

Referring to FIG. 1, in an exemplary embodiment, a block diagramillustrates a distributed security system 100. The system 100 may, forexample, be implemented as an overlay network in a wide area network(WAN), such as the Internet, a local area network (LAN), or the like.The system 100 includes content processing nodes, PN 110, thatproactively detect and preclude the distribution of security threats,e.g., malware, spyware, viruses, email spam, etc., and other undesirablecontent sent from or requested by an external system. Example externalsystems may include an enterprise 200, a computer device 220, and amobile device 230, or other network and computing systemscommunicatively coupled to the system 100. In an exemplary embodiment,each of the processing nodes 110 may include a decision system, e.g.,data inspection engines that operate on a content item, e.g., a webpage, a file, an email message, or some other data or data communicationthat is sent from or requested by one of the external systems. In anexemplary embodiment, all data destined for or received from theInternet is processed through one of the processing nodes 110. Inanother exemplary embodiment, specific data specified by each externalsystem, e.g., only email, only executable files, etc., is processthrough one of the processing node 110.

Each of the processing nodes 110 may generate a decision vector D=[d1,d2, . . . , dn] for a content item of one or more parts C=[c1, c2, . . ., cm]. Each decision vector may identify a threat classification, e.g.,clean, spyware, malware, undesirable content, innocuous, spam email,unknown, etc. For example, the output of each element of the decisionvector D may be based on the output of one or more data inspectionengines. In an exemplary embodiment, the threat classification may bereduced to a subset of categories, e.g., violating, non-violating,neutral, unknown. Based on the subset classification, the processingnode 110 may allow distribution of the content item, precludedistribution of the content item, allow distribution of the content itemafter a cleaning process, or perform threat detection on the contentitem. In an exemplary embodiment, the actions taken by one of theprocessing nodes 110 may be determinative on the threat classificationof the content item and on a security policy of the external system towhich the content item is being sent from or from which the content itemis being requested by. A content item is violating if, for any partC=[c1, c2, . . . , cm] of the content item, at any of the processingnodes 110, any one of the data inspection engines generates an outputthat results in a classification of “violating.”

Each of the processing nodes 110 may be implemented by one or more ofcomputer and communication devices, e.g., server computers, gateways,switches, etc., such as the server 300 described in FIG. 3. In anexemplary embodiment, the processing nodes 110 may serve as an accesslayer 150. The access layer 150 may, for example, provide externalsystem access to the security system 100. In an exemplary embodiment,each of the processing nodes 110 may include Internet gateways and oneor more servers, and the processing nodes 110 may be distributed througha geographic region, e.g., throughout a country, region, campus, etc.According to a service agreement between a provider of the system 100and an owner of an external system, the system 100 may thus providesecurity protection to the external system at any location throughoutthe geographic region.

Data communications may be monitored by the system 100 in a variety ofways, depending on the size and data requirements of the externalsystem. For example, an enterprise 200 may have multiple routers,switches, etc. that are used to communicate over the Internet, and therouters, switches, etc. may be configured to establish communicationsthrough the nearest (in traffic communication time, for example)processing node 110. A mobile device 230 may be configured tocommunicated to a nearest processing node 110 through any availablewireless access device, such as an access point, or a cellular gateway.A single computer device 220, such as a consumer's personal computer,may have its browser and email program configured to access the nearestprocessing node 110, which, in turn, serves as a proxy for the computerdevice 220. Alternatively, an Internet provider may have all of itscustomer traffic processed through the processing nodes 110.

In an exemplary embodiment, the processing nodes 110 may communicatewith one or more authority nodes (AN) 120. The authority nodes 120 maystore policy data for each external system and may distribute the policydata to each of the processing nodes 110. The policy may, for example,define security policies for a protected system, e.g., security policiesfor the enterprise 200. Example policy data may define access privilegesfor users, websites and/or content that is disallowed, restricteddomains, etc. The authority nodes 120 may distribute the policy data tothe processing nodes 110. In an exemplary embodiment, the authoritynodes 120 may also distribute threat data that includes theclassifications of content items according to threat classifications,e.g., a list of known viruses, a list of known malware sites, spam emaildomains, a list of known phishing sites, etc. The distribution of threatdata between the processing nodes 110 and the authority nodes 120 mayimplemented by push and pull distribution schemes described in moredetail below. In an exemplary embodiment, each of the authority nodes120 may be implemented by one or more computer and communicationdevices, e.g., server computers, gateways, switches, etc., such as theserver 300 described in FIG. 3. In some exemplary embodiments, theauthority nodes 120 may serve as an application layer 160. Theapplication layer 160 may, for example, manage and provide policy data,threat data, and data inspection engines and dictionaries for theprocessing nodes 110.

Other application layer functions may also be provided in theapplication layer 170, such as a user interface (UI) front-end 130. Theuser interface front-end 130 may provide a user interface through whichusers of the external systems may provide and define security policies,e.g., whether email traffic is to be monitored, whether certain websites are to be precluded, etc. Another application capability that maybe provided through the user interface front-end 130 is securityanalysis and log reporting. The underlying data on which the securityanalysis and log reporting functions operate are stored in logging nodes(LN) 140, which serve as the application layer 160. Each of the loggingnodes 140 may store data related to security operations and networktraffic processed by the processing nodes 110 for each external system.In an exemplary embodiment, the logging node 140 data may be anonymizedso that data identifying an enterprise is removed or obfuscated. Forexample, identifying data may be removed to provide an overall systemsummary of security processing for all enterprises and users withoutrevealing the identity of any one account. Alternatively, identifyingdata may be obfuscated, e.g., provide a random account number each timeit is accessed, so that an overall system summary of security processingfor all enterprises and users may be broken out by accounts withoutrevealing the identity of any one account. In another exemplaryembodiment, the identifying data and/or logging node 140 data may befurther encrypted, e.g., so that only the enterprise (or user if asingle user account) may have access to the logging node 140 data forits account. Other processes of anonymizing, obfuscating, or securinglogging node 140 data may also be used.

In an exemplary embodiment, an access agent 180 may be included in theexternal systems. For example, the access agent 180 is deployed in theenterprise 200. The access agent 180 may, for example, facilitatesecurity processing by providing a hash index of files on a clientdevice to one of the processing nodes 110, or may facilitateauthentication functions with one of the processing nodes 110, e.g., byassigning tokens for passwords and sending only the tokens to aprocessing node so that transmission of passwords beyond the networkedge of the enterprise is minimized. Other functions and processes mayalso be facilitated by the access agent 180. In an exemplary embodiment,the processing node 110 may act as a forward proxy that receives userrequests to external servers addressed directly to the processing node110. In another exemplary embodiment, the processing node 110 may accessuser requests that are passed through the processing node 110 in atransparent mode. A protected system, e.g., enterprise 200, may, forexample, choose one or both of these modes. For example, a browser maybe configured either manually or through the access agent 180 to accessthe processing node 110 in a forward proxy mode. In the forward proxymode, all accesses are addressed to the processing node 110.

In an exemplary embodiment, an enterprise gateway may be configured sothat user requests are routed through the processing node 110 byestablishing a communication tunnel between enterprise gateway and theprocessing node 110. For establishing the tunnel, existing protocolssuch as generic routing encapsulation (GRE), layer two tunnelingprotocol (L2TP), or other Internet Protocol (IP) security protocols maybe used. In another exemplary embodiment, the processing nodes 110 maybe deployed at Internet service provider (ISP) nodes. The ISP nodes mayredirect subject traffic to the processing nodes 110 in a transparentproxy mode. Protected systems, such as the enterprise 200, may use amultiprotocol label switching (MPLS) class of service for indicating thesubject traffic that is to be redirected. For example, at the within theenterprise the access agent 180 may be configured to perform MPLSlabeling. In another transparent proxy mode exemplary embodiment, aprotected system, such as the enterprise 200, may identify theprocessing node 110 as a next hop router for communication with theexternal servers.

Generally, the distributed security system 100 may generally refer to anexemplary cloud based security system. Cloud computing systems andmethods abstract away physical servers, storage, networking, etc. andinstead offer these as on-demand and elastic resources. The NationalInstitute of Standards and Technology (NIST) provides a concise andspecific definition which states cloud computing is a model for enablingconvenient, on-demand network access to a shared pool of configurablecomputing resources (e.g., networks, servers, storage, applications, andservices) that can be rapidly provisioned and released with minimalmanagement effort or service provider interaction. Cloud computingdiffers from the classic client-server model by providing applicationsfrom a server that are executed and managed by a client's web browser,with no installed client version of an application required.Centralization gives cloud service providers complete control over theversions of the browser-based applications provided to clients, whichremoves the need for version upgrades or license management onindividual client computing devices. The phrase “software as a service”(SaaS) is sometimes used to describe application programs offeredthrough cloud computing. A common shorthand for a provided cloudcomputing service (or even an aggregation of all existing cloudservices) is “the cloud.” The distributed security system 100 isillustrated herein as one exemplary embodiment of a cloud based system,and those of ordinary skill in the art will recognize the cloud basedmobile device security and policy systems and methods contemplateoperation on any cloud based system.

Referring to FIG. 2, in an exemplary embodiment, a block diagramillustrates various components of the distributed security system 100 inmore detail. Although FIG. 2 illustrates only one representativecomponent processing node 110, authority node 120 and logging node 140,those of ordinary skill in the art will appreciate there may be many ofeach of the component nodes 110, 120 and 140 present in the system 100.A wide area network (WAN) 101, such as the Internet, or some othercombination of wired and/or wireless networks, communicatively couplesthe processing node 110, the authority node 120, and the logging node140 therebetween. The external systems 200, 220 and 230 likewisecommunicate over the WAN 101 with each other or other data providers andpublishers. Some or all of the data communication of each of theexternal systems 200, 220 and 230 may be processed through theprocessing node 110.

FIG. 2 also shows the enterprise 200 in more detail. The enterprise 200may, for example, include a firewall (FW) 202 protecting an internalnetwork that may include one or more enterprise servers 216, alightweight directory access protocol (LDAP) server 212, and other dataor data stores 214. Another firewall 203 may protect an enterprisesubnet that can include user computers/servers 206 and 208 (e.g., laptopand desktop computers). The enterprise 200 may communicate with the WAN101 through one or more network devices, such as a router, gateway,switch, etc. The LDAP server 212 may store, for example, user logincredentials for registered users of the enterprise 200 system. Suchcredentials may include user identifiers, login passwords, and a loginhistory associated with each user identifier. The other data stores 214may include sensitive information, such as bank records, medicalrecords, trade secret information, or any other information warrantingprotection by one or more security measures.

In an exemplary embodiment, a client access agent 180 a may be includedon a client computer 208. The client access agent 180 a may, forexample, facilitate security processing by providing a hash index offiles on the user computer 208 to a processing node 110 for malware,virus detection, etc. Other security operations may also be facilitatedby the access agent 180 a. In another exemplary embodiment, a serveraccess agent 180 may facilitate authentication functions with theprocessing node 110, e.g., by assigning tokens for passwords and sendingonly the tokens to the processing node 110 so that transmission ofpasswords beyond the network edge of the enterprise 200 is minimized.Other functions and processes may also be facilitated by the serveraccess agent 180 b. The computer device 220 and the mobile device 230may also store information warranting security measures, such aspersonal bank records, medical information, and login information, e.g.,login information to the server 206 of the enterprise 200, or to someother secured data provider server. The computer device 220 and themobile device 230 can also store information warranting securitymeasures, such as personal bank records, medical information, and logininformation, e.g., login information to a server 216 of the enterprise200, or to some other secured data provider server.

In an exemplary embodiment, the processing nodes 110 are external tonetwork edges of the external systems 200, 220 and 230. Each of theprocessing nodes 110 stores security policy data 113 received from theauthority node 120 and monitors content items requested by or sent fromthe external systems 200, 220 and 230. In an exemplary embodiment, eachof the processing nodes 110 may also store a detection process filter112 and/or threat data 114 to facilitate the decision of whether acontent item should be processed for threat detection. A processing nodemanager 118 may manage each content item in accordance with the securitypolicy data 113, and the detection process filter 112 and/or threat data114, if stored at the processing node 110, so that security policies fora plurality of external systems in data communication with theprocessing node 110 are implemented external to the network edges foreach of the external systems 200, 220 and 230. For example, depending onthe classification resulting from the monitoring, the content item maybe allowed, precluded, or threat detected. In general, content itemsthat are already classified as “clean” or not posing a threat can beallowed, while those classified as “violating” may be precluded. Thosecontent items having an unknown status, e.g., content items that havenot been processed by the system 100, may be threat detected to classifythe content item, according to threat classifications.

The processing node 110 may include a state manager 116A. The statemanager 116A may be used to maintain the authentication and theauthorization states of users that submit requests to the processingnode 110. Maintenance of the states through the state manager 116A mayminimize the number of authentication and authorization transactionsthat are necessary to process a request. The processing node 110 mayalso include an epoch processor 116B. The epoch processor 116B may beused to analyze authentication data that originated at the authoritynode 120. The epoch processor 116B may use an epoch ID to validatefurther the authenticity of authentication data. The processing node 110may further include a source processor 116C. The source processor 116Cmay be used to verify the source of authorization and authenticationdata. The source processor 116C may identify improperly obtainedauthorization and authentication data, enhancing the security of thenetwork. Collectively, the state manager 116A, the epoch processor 116B,and the source processor 116C operate as data inspection engines.

Because the amount of data being processed by the processing nodes 110may be substantial, the detection processing filter 112 may be used asthe first stage of an information lookup procedure. For example, thedetection processing filter 112 may be used as a front end to a lookingof the threat data 114. Content items may be mapped to index values ofthe detection processing filter 112 by a hash function that operates onan information key derived from the information item. The informationkey is hashed to generate an index value (i.e., a bit position). A valueof zero in a bit position in the guard table can indicate, for example,the absence of information, while a one in that bit position canindicate the presence of information. Alternatively, a one could be usedto represent absence, and a zero to represent presence. Each contentitem may have an information key that is hashed. For example, theprocessing node manager 118 may identify the Uniform Resource Locator(URL) address of URL requests as the information key and hash the URLaddress; or may identify the file name and the file size of anexecutable file information key and hash the file name and file size ofthe executable file. Hashing an information key to generate an index andchecking a bit value at the index in the detection processing filter 112generally requires less processing time than actually searching threatdata 114. The use of the detection processing filter 112 may improve thefailure query (i.e., responding to a request for absent information)performance of database queries and/or any general information queries.Because data structures are generally optimized to access informationthat is present in the structures, failure query performance has agreater effect on the time required to process information searches forvery rarely occurring items, e.g., the presence of file information in avirus scan log or a cache where many or most of the files transferred ina network have not been scanned or cached. Using the detectionprocessing filter 112, however, the worst case additional cost is onlyon the order of one, and thus its use for most failure queries saves onthe order of m log m, where m is the number of information recordspresent in the threat data 114.

The detection processing filter 112 thus improves performance of querieswhere the answer to a request for information is usually positive. Suchinstances may include, for example, whether a given file has been virusscanned, whether content at a given URL has been scanned forinappropriate (e.g., pornographic) content, whether a given fingerprintmatches any of a set of stored documents, and whether a checksumcorresponds to any of a set of stored documents. Thus, if the detectionprocessing filter 112 indicates that the content item has not beenprocessed, then a worst case null lookup operation into the threat data114 is avoided, and a threat detection can be implemented immediately.The detection processing filter 112 thus complements the threat data 114that capture positive information. In an exemplary embodiment, thedetection processing filter 112 may be a Bloom filter implemented by asingle hash function. The Bloom filter may be sparse table, i.e., thetables include many zeros and few ones, and the hash function is chosento minimize or eliminate false negatives which are, for example,instances, where an information key is hashed to a bit position and thatbit position, indicates that the requested information is absent when itis actually present.

In general, the authority node 120 includes a data store that storesmaster security policy data 123 for each of the external systems 200,220 and 230. An authority node manager 128 may be used to manage themaster security policy data 123, e.g., receive input from users of eachof the external systems defining different security policies, and maydistribute the master security policy data 123 to each of the processingnodes 110. The processing nodes 110 then store a local copy of thesecurity policy data 113. The authority node 120 may also store a masterdetection process filter 122. The detection processing filter 122 mayinclude data indicating whether content items have been processed by oneor more of the data inspection engines 116 in any of the processingnodes 110. The authority node manager 128 may be used to manage themaster detection processing filter 122, e.g., receive updates from aprocessing nodes 110 when the processing node 110 has processed acontent item and update the master detection processing filter 122. Forexample, the master detection processing filter 122 may be distributedto the processing nodes 110, which then store a local copy of thedetection processing filter 112.

In an exemplary embodiment, the authority node 120 may include an epochmanager 126. The epoch manager 126 may be used to generateauthentication data associated with an epoch ID. The epoch ID of theauthentication data is a verifiable attribute of the authentication datathat can be used to identify fraudulently created authentication data.In an exemplary embodiment, the detection processing filter 122 may be aguard table. The processing node 110 may, for example, use theinformation in the local detection processing filter 112 to quicklydetermine the presence and/or absence of information, e.g., whether aparticular URL has been checked for malware; whether a particularexecutable has been virus scanned, etc. The authority node 120 may alsostore master threat data 124. The master threat data 124 may classifycontent items by threat classifications, e.g., a list of known viruses,a list of known malware sites, spam email domains, list of known ordetected phishing sites, etc. The authority node manager 128 may be usedto manage the master threat data 124, e.g., receive updates from theprocessing nodes 110 when one of the processing nodes 110 has processeda content item and update the master threat data 124 with any pertinentresults. In some implementations, the master threat data 124 may bedistributed to the processing nodes 110, which then store a local copyof the threat data 114. In another exemplary embodiment, the authoritynode 120 may also monitor the health of each of the processing nodes110, e.g., the resource availability in each of the processing nodes110, detection of link failures, etc. Based on the observed health ofeach of the processing nodes 110, the authority node 120 may redirecttraffic among the processing nodes 110 and/or balance traffic among theprocessing nodes 110. Other remedial actions and processes may also befacilitated by the authority node 120.

The processing node 110 and the authority node 120 may be configuredaccording to one or more push and pull processes to manage content itemsaccording to security policy data 113 and/or 123, detection processingfilters 112 and/or 122, and the threat data 114 and/or 124. In a threatdata push implementation, each of the processing nodes 110 stores policydata 113 and threat data 114. The processing node manager 118 determineswhether a content item requested by or transmitted from an externalsystem is classified by the threat data 114. If the content item isdetermined to be classified by the threat data 114, then the processingnode manager 118 may manage the content item according to the securityclassification of the content item and the security policy of theexternal system. If, however, the content item is determined to not beclassified by the threat data 114, then the processing node manager 118may cause one or more of the data inspection engines 117 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120.

The authority node manager 128, in response to receiving the threat dataupdate, updates the master threat data 124 stored in the authority nodedata store according to the threat data update received from theprocessing node 110. In an exemplary embodiment, the authority nodemanager 128 may automatically transmit the updated threat data to theother processing nodes 110. Accordingly, threat data for new threats asthe new threats are encountered are automatically distributed to eachprocessing node 110. Upon receiving the new threat data from theauthority node 120, each of processing node managers 118 may store theupdated threat data in the locally stored threat data 114.

In a threat data pull and push implementation, each of the processingnodes 110 stores policy data 113 and threat data 114. The processingnode manager 118 determines whether a content item requested by ortransmitted from an external system is classified by the threat data114. If the content item is determined to be classified by the threatdata 114, then the processing node manager 118 may manage the contentitem according to the security classification of the content item andthe security policy of the external system. If, however, the contentitem is determined to not be classified by the threat data, then theprocessing node manager 118 may request responsive threat data for thecontent item from the authority node 120. Because processing a contentitem may consume valuable resource and time, in some implementations theprocessing node 110 may first check with the authority node 120 forthreat data 114 before committing such processing resources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node data store. If responsivethreat data is stored in the master threat data 124, then the authoritynode manager 128 provide a reply that includes the responsive threatdata to the processing node 110 so that the processing node manager 118may manage the content item in accordance with the security policy data113 and the classification of the content item. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118can cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120. The authority node manager 128 can then update themaster threat data 124. Thereafter, any future requests related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

In a detection process filter and threat data push implementation, eachof the processing nodes 110 stores a detection process filter 112,policy data 113, and threat data 114. The processing node manager 118accesses the detection process filter 112 to determine whether thecontent item has been processed. If the processing node manager 118determines that the content item has been processed, it may determine ifthe content item is classified by the threat data 114. Because thedetection process filter 112 has the potential for a false positive, alookup in the threat data 114 may be implemented to ensure that a falsepositive has not occurred. The initial check of the detection processfilter 112, however, may eliminate many null queries to the threat data114, which, in turn, conserves system resources and increasesefficiency. If the content item is classified by the threat data 114,then the processing node manager 118 may manage the content item inaccordance with the security policy data 113 and the classification ofthe content item. Conversely, if the processing node manager 118determines that the content item is not classified by the threat data114, or if the processing node manager 118 initially determines throughthe detection process filter 112 that the content item is not classifiedby the threat data 114, then the processing node manager 118 may causeone or more of the data inspection engines 116 to perform the threatdetection processes to classify the content item according to a threatclassification. Once the content item is classified, the processing nodemanager 118 generates a threat data update that includes data indicatingthe threat classification for the content item from the threat detectionprocess, and transmits the threat data update to one of the authoritynodes 120.

The authority node manager 128, in turn, may update the master threatdata 124 and the master detection process filter 122 stored in theauthority node data store according to the threat data update receivedfrom the processing node 110. In an exemplary embodiment, the authoritynode manager 128 may automatically transmit the updated threat data anddetection processing filter to other processing nodes 110. Accordingly,threat data and the detection processing filter for new threats as thenew threats are encountered are automatically distributed to eachprocessing node 110, and each processing node 110 may update its localcopy of the detection processing filter 112 and threat data 114.

In a detection process filter and threat data pull and pushimplementation, each of the processing nodes 110 stores a detectionprocess filter 112, policy data 113, and threat data 114. The processingnode manager 118 accesses the detection process filter 112 to determinewhether the content item has been processed. If the processing nodemanager 118 determines that the content item has been processed, it maydetermine if the content item is classified by the threat data 114.Because the detection process filter 112 has the potential for a falsepositive, a lookup in the threat data 114 can be implemented to ensurethat a false positive has not occurred. The initial check of thedetection process filter 112, however, may eliminate many null queriesto the threat data 114, which, in turn, conserves system resources andincreases efficiency. If the processing node manager 118 determines thatthe content item has not been processed, it may request responsivethreat data for the content item from the authority node 120. Becauseprocessing a content item may consume valuable resource and time, insome implementations the processing node 110 may first check with theauthority node 120 for threat data 114 before committing such processingresources.

The authority node manager 128 may receive the responsive threat datarequest from the processing node 110 and may determine if the responsivethreat data is stored in the authority node 120 data store. Ifresponsive threat data is stored in the master threat data 124, then theauthority node manager 128 provides a reply that includes the responsivethreat data to the processing node 110 so that the processing nodemanager 118 can manage the content item in accordance with the securitypolicy data 113 and the classification of the content item, and furtherupdate the local detection processing filter 112. Conversely, if theauthority node manager 128 determines that responsive threat data is notstored in the master threat data 124, then the authority node manager128 may provide a reply that does not include the responsive threat datato the processing node 110. In response, the processing node manager 118may cause one or more of the data inspection engines 116 to perform thethreat detection processes to classify the content item according to athreat classification. Once the content item is classified, theprocessing node manager 118 generates a threat data update that includesdata indicating the threat classification for the content item from thethreat detection process, and transmits the threat data update to anauthority node 120. The authority node manager 128 may then update themaster threat data 124. Thereafter, any future requests for related toresponsive threat data for the content item from other processing nodes110 can be readily served with responsive threat data.

The various push and pull data exchange processes provided above areexemplary processes for which the threat data and/or detection processfilters may be updated in the system 100 of FIGS. 1 and 2. Other updateprocesses, however, are contemplated with the present invention. Thedata inspection engines 116, processing node manager 118, authority nodemanager 128, user interface manager 132, logging node manager 148, andaccess agent 180 may be realized by instructions that upon executioncause one or more processing devices to carry out the processes andfunctions described above. Such instructions can, for example, includeinterpreted instructions, such as script instructions, e.g., JavaScriptor ECMAScript instructions, or executable code, or other instructionsstored in a non-transitory computer readable medium. Other processingarchitectures can also be used, e.g., a combination of speciallydesigned hardware and software, for example.

Referring to FIG. 3, in an exemplary embodiment, a block diagramillustrates a server 300 which may be used in the system 100 orstandalone. Any of the processing nodes 110, the authority nodes 120,and the logging nodes 140 may be formed through one or more servers 300.Further, the computer device 220, the mobile device 230, the servers208, 216, etc. may include the server 300. The server 300 may be adigital computer that, in terms of hardware architecture, generallyincludes a processor 302, input/output (I/O) interfaces 304, a networkinterface 306, a data store 308, and memory 310. It should beappreciated by those of ordinary skill in the art that FIG. 3 depictsthe server 300 in an oversimplified manner, and a practical embodimentmay include additional components and suitably configured processinglogic to support known or conventional operating features that are notdescribed in detail herein. The components (302, 304, 306, 308, and 310)are communicatively coupled via a local interface 312. The localinterface 312 may be, for example, but not limited to, one or more busesor other wired or wireless connections, as is known in the art. Thelocal interface 312 may have additional elements, which are omitted forsimplicity, such as controllers, buffers (caches), drivers, repeaters,and receivers, among many others, to enable communications. Further, thelocal interface 312 may include address, control, and/or dataconnections to enable appropriate communications among theaforementioned components.

The processor 302 is a hardware device for executing softwareinstructions. The processor 302 may be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the server 300, asemiconductor-based microprocessor (in the form of a microchip or chipset), or generally any device for executing software instructions. Whenthe server 300 is in operation, the processor 302 is configured toexecute software stored within the memory 310, to communicate data toand from the memory 310, and to generally control operations of theserver 300 pursuant to the software instructions. The I/O interfaces 304may be used to receive user input from and/or for providing systemoutput to one or more devices or components. User input may be providedvia, for example, a keyboard, touchpad, and/or a mouse. The systemoutput may be provided via a display device and a printer (not shown).I/O interfaces 304 can include, for example, a serial port, a parallelport, a small computer system interface (SCSI), an infrared (IR)interface, a radio frequency (RF) interface, and/or a universal serialbus (USB) interface.

The network interface 306 may be used to enable the server 300 tocommunicate on a network, such as the Internet, the WAN 101, theenterprise 200, and the like, etc. The network interface 306 mayinclude, for example, an Ethernet card or adapter (e.g., 10BaseT, FastEthernet, Gigabit Ethernet, 10 GbE) or a wireless local area network(WLAN) card or adapter (e.g., 802.11a/b/g/n). The network interface 306may include address, control, and/or data connections to enableappropriate communications on the network. A data store 308 may be usedto store data. The data store 308 may include any of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,and the like)), nonvolatile memory elements (e.g., ROM, hard drive,tape, CDROM, and the like), and combinations thereof. Moreover, the datastore 308 may incorporate electronic, magnetic, optical, and/or othertypes of storage media. In one example, the data store 1208 may belocated internal to the server 300 such as, for example, an internalhard drive connected to the local interface 312 in the server 300.Additionally in another embodiment, the data store 308 may be locatedexternal to the server 300 such as, for example, an external hard driveconnected to the I/O interfaces 304 (e.g., SCSI or USB connection). In afurther embodiment, the data store 308 may be connected to the server300 through a network, such as, for example, a network attached fileserver.

The memory 310 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, tape, CDROM, etc.), andcombinations thereof. Moreover, the memory 310 may incorporateelectronic, magnetic, optical, and/or other types of storage media. Notethat the memory 310 may have a distributed architecture, where variouscomponents are situated remotely from one another, but can be accessedby the processor 302. The software in memory 310 may include one or moresoftware programs, each of which includes an ordered listing ofexecutable instructions for implementing logical functions. The softwarein the memory 310 includes a suitable operating system (0/S) 314 and oneor more programs 316. The operating system 314 essentially controls theexecution of other computer programs, such as the one or more programs316, and provides scheduling, input-output control, file and datamanagement, memory management, and communication control and relatedservices. The operating system 314 may be any of Windows NT, Windows2000, Windows XP, Windows Vista, Windows 7, Windows Server 2003/2008(all available from Microsoft, Corp. of Redmond, Wash.), Solaris(available from Sun Microsystems, Inc. of Palo Alto, Calif.), LINUX (oranother UNIX variant) (available from Red Hat of Raleigh, N.C.), Androidand variants thereof (available from Google, Inc. of Mountain View,Calif.), Apple OS X and variants thereof (available from Apple, Inc. ofCupertino, Calif.), or the like. The one or more programs 316 may beconfigured to implement the various processes, algorithms, methods,techniques, etc. described herein.

Referring to FIG. 4, in an exemplary embodiment, a block diagramillustrates a mobile device 400, which may be used in the system 100 orthe like. The mobile device 400 can be a digital device that, in termsof hardware architecture, generally includes a processor 412,input/output (I/O) interfaces 414, a radio 416, a data store 418, andmemory 422. It should be appreciated by those of ordinary skill in theart that FIG. 4 depicts the mobile device 410 in an oversimplifiedmanner, and a practical embodiment may include additional components andsuitably configured processing logic to support known or conventionaloperating features that are not described in detail herein. Thecomponents (412, 414, 416, 418, and 422) are communicatively coupled viaa local interface 424. The local interface 424 can be, for example, butnot limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The local interface 424 can haveadditional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, amongmany others, to enable communications. Further, the local interface 424may include address, control, and/or data connections to enableappropriate communications among the aforementioned components.

The processor 412 is a hardware device for executing softwareinstructions. The processor 412 can be any custom made or commerciallyavailable processor, a central processing unit (CPU), an auxiliaryprocessor among several processors associated with the mobile device410, a semiconductor-based microprocessor (in the form of a microchip orchip set), or generally any device for executing software instructions.When the mobile device 410 is in operation, the processor 412 isconfigured to execute software stored within the memory 422, tocommunicate data to and from the memory 422, and to generally controloperations of the mobile device 410 pursuant to the softwareinstructions. In an exemplary embodiment, the processor 412 may includea mobile-optimized processor such as optimized for power consumption andmobile applications. The I/O interfaces 414 can be used to receive userinput from and/or for providing system output. User input can beprovided via, for example, a keypad, a touch screen, a scroll ball, ascroll bar, buttons, barcode scanner, and the like. System output can beprovided via a display device such as a liquid crystal display (LCD),touch screen, and the like. The I/O interfaces 414 can also include, forexample, a serial port, a parallel port, a small computer systeminterface (SCSI), an infrared (IR) interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, and the like. The I/Ointerfaces 414 can include a graphical user interface (GUI) that enablesa user to interact with the mobile device 410. Additionally, the I/Ointerfaces 414 may further include an imaging device, i.e. camera, videocamera, etc.

The radio 416 enables wireless communication to an external accessdevice or network. Any number of suitable wireless data communicationprotocols, techniques, or methodologies can be supported by the radio416, including, without limitation: RF; IrDA (infrared); Bluetooth;ZigBee (and other variants of the IEEE 802.15 protocol); IEEE 802.11(any variation); IEEE 802.16 (WiMAX or any other variation); DirectSequence Spread Spectrum; Frequency Hopping Spread Spectrum; Long TermEvolution (LTE); cellular/wireless/cordless telecommunication protocols(e.g. 3G/4G, etc.); wireless home network communication protocols;paging network protocols; magnetic induction; satellite datacommunication protocols; wireless hospital or health care facilitynetwork protocols such as those operating in the WMTS bands; GPRS;proprietary wireless data communication protocols such as variants ofWireless USB; and any other protocols for wireless communication. Thedata store 418 may be used to store data. The data store 418 may includeany of volatile memory elements (e.g., random access memory (RAM, suchas DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g.,ROM, hard drive, tape, CDROM, and the like), and combinations thereof.Moreover, the data store 418 may incorporate electronic, magnetic,optical, and/or other types of storage media.

The memory 422 may include any of volatile memory elements (e.g., randomaccess memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatilememory elements (e.g., ROM, hard drive, etc.), and combinations thereof.Moreover, the memory 422 may incorporate electronic, magnetic, optical,and/or other types of storage media. Note that the memory 422 may have adistributed architecture, where various components are situated remotelyfrom one another, but can be accessed by the processor 412. The softwarein memory 422 can include one or more software programs, each of whichincludes an ordered listing of executable instructions for implementinglogical functions. In the example of FIG. 4, the software in the memorysystem 422 includes a suitable operating system (O/S) 426 and programs428. The operating system 426 essentially controls the execution ofother computer programs and provides scheduling, input-output control,file and data management, memory management, and communication controland related services. The operating system 426 may be any of LINUX (oranother UNIX variant), Android (available from Google), Symbian OS,Microsoft Windows CE, Microsoft Windows 7 Mobile, iOS (available fromApple, Inc.), webOS (available from Hewlett Packard), Blackberry OS(Available from Research in Motion), and the like. The programs 428 mayinclude various applications, add-ons, etc. configured to provide enduser functionality with the mobile device 400. For example, exemplaryprograms 428 may include, but not limited to, a web browser, socialnetworking applications, streaming media applications, games, mappingand location applications, electronic mail applications, financialapplications, and the like. In a typical example, the end user typicallyuses one or more of the programs 428 along with a network such as thesystem 100.

Referring to FIG. 5, in an exemplary embodiment, a cloud system 500 isillustrated for implementing cloud based mobile device security andpolicy systems and methods and cloud based MDM systems and methods. Thecloud system 500 includes one or more cloud nodes (CN) 502communicatively coupled to the Internet 504. The cloud nodes 502 mayinclude the processing nodes 110, the server 300, or the like. That is,the cloud system 500 may include the distributed security system 100 oranother implementation of a cloud based system. In the cloud system 500,traffic from various locations such as a regional office 510,headquarters 520, various employee's homes 530, mobile laptop 540, andmobile device 550 is redirected to the cloud through the cloud nodes502. That is, each of the locations 510, 520, 530, 540, 550 iscommunicatively coupled to the Internet 504 through the cloud nodes 502.The cloud system 500 may be configured to perform various functions suchas spam filtering, uniform resource locator (URL) filtering, antivirusprotection, bandwidth control, data loss prevention, zero-dayvulnerability protection, web 2.0 features, and the like. In anexemplary embodiment, the cloud system 500 and the distributed securitysystem 100 may be viewed as Security-as-a-Service through the cloud.

In various exemplary embodiments, the cloud system 500 is configured toprovide mobile device security and policy systems and methods. Themobile device 550 may be the mobile device 400, and may include commondevices such as smartphones, tablets, netbooks, personal digitalassistants, MP3 players, cell phones, e-book readers, and the like. Thecloud system 500 is configured to provide security and policyenforcement for devices including the mobile devices 550 in the cloud.Advantageously, the cloud system 500 avoids platform-specific securityapps on the mobile devices 550, forwards web traffic through the cloudsystem 500, enables network administrators to define policies in thecloud, and enforces/cleans traffic in the cloud prior to delivery to themobile devices 550. Further, through the cloud system 500, networkadministrators may define user-centric policies tied to users, notdevices, with the policies being applied regardless of the device usedby the user. The cloud system 500 provides 24×7 security with no needfor updates as the cloud system 500 is always up-to-date with currentthreats and without requiring device signature updates. Also, the cloudsystem 500 enables multiple enforcement points, centralized provisioningand logging, automatic traffic routing to a nearest cloud node 502,geographical distribution of the cloud nodes 502, policy shadowing ofusers which is dynamically available at the cloud nodes, etc.

In other exemplary embodiments, the cloud system 500 is configured toprovide MDM functionality for mobile devices such as the mobile device550. The cloud based MDM systems and methods provide an ability tomanage the mobile device 550 and other mobile devices with or without anMDM client on the mobile device 550 and without an appliance or serverat the enterprise (i.e. at the regional office 510 or the headquarters520). In an exemplary embodiment, a client-less implementation leveragesthe ActiveSync protocol, proxied through the distributed cloud nodes 502to enforce basic policies e.g. password, screen lock, remote wipe,enable/disable features such as the browser or camera, etc. In anotherexemplary embodiment, a client-based implementation uses a specificplatform application and associated API to connect with the mobiledevice 550 and provide MDM features. The cloud system 500 providesscalability, redundancy, and reduced latency with the multiplegeographically distributed cloud nodes 502. MDM policies may be definedin a Central Authority (CA) 560 that pushes then out, on-demand, togeographically distributed cloud nodes 502. The mobile devices 550communicate with local cloud nodes 502 without requiring configurationchanges, e.g. the mobile devices 550 may be automatically directed tothe closest cloud node 502. Policies are automatically available at thelocal cloud node 502 minimizing latency. In the event of cloud node 502failure or excessive load, connections are load balanced automaticallyacross other cloud nodes 502, transparent to the mobile device 550.

ActiveSync is a mobile data synchronization technology and protocoldeveloped by Microsoft. ActiveSync works over hypertext transferprotocol (HTTP) and HTTPS and is licensed by several mobile devicemanufacturers such as Apple, Google, etc. ActiveSync email client ispre-installed on most mobile devices 550 today. ActiveSync allows emailand policy sync. Generally, there are two implementations of ActiveSync.A first implementation synchronizes data and information with mobiledevices 550 and a specific computer. A second implementation commonlyknown as Exchange ActiveSync (EAS) provides push synchronization ofcontacts, calendars, tasks, email, and the like between servers and themobile devices 550. Exchange ActiveSync runs over HTTP(S) using WirelessApplication Protocol (WAP) binary Extensible markup language (XML). WAPbinary XML is a binary format that encodes the parsed physical form ofan XML document, i.e., the structure and content of the documententities. Meta-information, including the document type definition andconditional sections, is removed when the document is converted to thebinary format. This provides a compact binary representation optimizedfor wireless applications.

In exemplary embodiments, the cloud nodes 502 may be configured tointercept or spoof Exchange ActiveSync messages. In an exemplaryembodiment, if a mobile device 550 has an ActiveSync association, suchas with a server at the headquarters 520, the cloud node 502 can proxythis connection blocking it if non-compliant and optionally insertpolicy provisioning commands. In another exemplary embodiment, if themobile device 550 does not have an Exchange ActiveSync association, thecloud node 502 can be configured to emulate or spoof an ExchangeActiveSync server and issue policy provisioning commands to the mobiledevice 550. In yet another exemplary embodiment, the mobile device 550may be provisioned with a platform specific MDM API, which interfaces tothe cloud node 502. The cloud based MDM systems and methods aredescribed herein with exemplary embodiments referencing ExchangeActiveSync for illustration, and those of ordinary skill in the art willrecognize this may include any synchronization techniques between themobile device 550 and the cloud nodes 502 including WAP binary XML andthe like. Fundamentally, the cloud based MDM systems and methods seek toutilize one or more existing synchronization techniques with the cloudsystem 500 for providing MDM functionality.

Referring to FIG. 6, in an exemplary embodiment, a flowchart and anetwork diagram illustrate an Exchange ActiveSync provisioning method600 for the cloud system 500. In particular, the provisioning method 600assumes the mobile device 550 does not have an Exchange ActiveSyncassociation, and the cloud node 502 is configured to emulate or spoof anExchange ActiveSync server and issue policy provisioning commands. Forthe provisioning method 600, an administrator specifies mobile users andtheir associated mobile devices 550 in a company's active directory(step 602). Active Directory (AD) is a service created by Microsoft thatuses standardized protocols to provide a variety of network services,including Lightweight Directory Access Protocol (LDAP), Kerberos-basedauthentication, Domain Name System (DNS)-based naming and other networkinformation, and the like. Features of the active directory include acentralized location for network administration and security,information security and single sign-on for user access to networkedresources, scalability, standardized access to application data, and thelike. The CA 560 synchronizes with the company's active directory (step604). Specifically, the CA 560 obtains user credentials for associatedmobile devices 550 in a company's active directory. Each of the mobileusers receives a notification to sign up for the cloud MDM (step 606).This may include a plurality of methods for the notification includingan email, a text message, offline instructions, and the like.

Through the sign up, the user adds ActiveSync email, e.g.user@company.com and a server, e.g. gateway.zscaler.net (step 608).Here, the user's mobile device 550 is configured to set up an ExchangeActiveSync connection with the server gateway.zscaler.net, i.e. thecloud node 502. DNS resolution for gateway.zscaler.net is done by thecloud service such that the resolved IP address points the mobile deviceto the nearest cloud node 502. Once connected, the cloud node 502 isconfigured to implement the ActiveSync protocol with the mobile device550 and the cloud node 502 requests authentication from the CA 560 (step610). Here, the CA 560 provides the cloud node 502 with the applicableauthentication data as well as configuration data for MDM. Finally, uponsuccessful authentication, an ActiveSync account is provisioned betweenthe mobile device 550 and the cloud node 502 (step 612). The cloud node502 utilizes this ActiveSync account to provide MDM of the mobile device550.

Referring to FIG. 7, in an exemplary embodiment, a flowchart and anetwork diagram illustrate Exchange ActiveSync based MDM method 700 forthe cloud system 500. For the MDM method 700, an administrator specifiesmobile policy profiles and applies it to users/groups of mobile devices550 (step 704). In the provisioning method 700, the mobile device 550 isalready set up with an ActiveSync account on the Exchange server 702.The mobile device 550 checks the cloud node 502 “ActiveSync Server” formailbox/policy updates (step 706). In an exemplary embodiment, the cloudnode 502 may be configured to operate as an “ActiveSync Server” to themobile device 550. In another exemplary embodiment, the cloud node 502may be configured to monitor and update ActiveSync messages between themobile device 550 and the Exchange server 702 and issue policyprovisioning commands therein. In either embodiment, the mobile device550 is communicatively coupled to the Exchange server 702 through thecloud node 502. The cloud node 502 may check the CA 560 for any policyupdates for the user (step 708). Specifically, the administrator maydefine the policy for the user through the CA 560. The cloud node“ActiveSync Server” sends provisioning payload information to the mobiledevice 550 (step 710).

Additionally, the mobile device 550 may be configured to get an emailfrom the actual company.com Exchange server 702 (step 712).Specifically, the mobile device 550 may have an ActiveSync associationwith the cloud node 502 and another with the Exchange server 702. If theActiveSync association is with the Exchange server 702, the cloud node502 may be configured to monitor for ActiveSync messages for compliancewith policy and to add information for provisioning, etc. In eitherembodiment, the cloud node 502 may be configured to proxy ActiveSyncmessages between the mobile device 550 and the Exchange server 702 (step714). If the ActiveSync messages do not comply with defined policy, thecloud node 502 may be configured to block email traffic from theExchange server 702 to the mobile device 550. Finally, the administratorhas access to various information related to MDM such as reports ofmissing devices, reports of non-compliant devices, etc. (step 716). Inparticular, the cloud node 502 is configured to proxy ActiveSyncmessages from the Exchange server 702. In an exemplary embodimentwithout the Exchange server 702, the cloud node 502 is configured tospoof policy messages of the ActiveSync protocol. With the Exchangeserver 702, then cloud node 502 is proxying the traffic and in theprocess can insert MDM policy messages in the stream.

Using Exchange ActiveSync with the cloud node 502 and the mobile device550, the provisioning method 600 and the MDM method 700 may utilize thebuilt-in support for ActiveSync among many existing mobile devices 550.For example, mobile devices 550 with built-in or native operating systemsupport for Exchange ActiveSync include Apple iPhone, iPad, Androiddevices, Palm OS, Symbian devices, Microsoft platforms, and the like.Using ActiveSync, the cloud based MDM systems and methods can performvarious functions, policies, etc. including, for example, remote wipe ofthe mobile device 550, password enforcement on the mobile device 550,locking the mobile device 550 based on inactivity, a refresh intervalfor policy updates, requiring manual synchronization such as whileroaming, preventing use of the camera, etc. For example, related to thepassword enforcement, the cloud based MDM systems and methods canenforce a minimum password length, set a number of failed passwordattempts before locking the mobile device 550 or performing a localwipe, require a mixture of characters in the password, set a passwordexpiration period and keep a password history to prevent new passwordsfrom matching previous passwords, and the like.

The cloud based MDM systems and methods can implement various additionalfunctions, features, policies, etc. such as instantaneous policychanges, scheduled policy changes, device backup, device settings, andthe like. Further, the cloud based MDM systems and methods canallow/disallow various functions of the mobile device 550 including, forexample, installation of specified applications, use of specifiedapplications, prevention of screen capture, prevention of voice dialing,prevention of games, prevention of social media, prevention of streamingmedia, web browser usage, prevention of Wi-Fi and/or Bluetooth, and thelike. Also, the cloud based MDM systems and methods may further provideprovisioning of various functions and features on the mobile device 550including, for example, Wi-Fi settings, virtual private network (VPN)settings, email settings, provisioning of credentials and the like, MDMsettings, wireless (e.g., GSM/CDMA, 4G) settings, and the like.

Referring to FIG. 8, in an exemplary embodiment, a flowchart and anetwork diagram illustrate a platform specific MDM configuration 800 forthe cloud system 500. In an exemplary embodiment, the platform specificMDM configuration 800 operates with a push notification server 802 and athird party MDM server 804 each in communication with the mobile device550. In another exemplary embodiment, the platform specific MDMconfiguration 800 may include the cloud node 502 performing thefunctions of both the push notification server 802 and the platformspecific MDM server 804. The platform specific MDM configuration 800begins with a configuration profile containing MDM server informationbeing sent to the mobile device 550 (step 812). The user of the mobiledevice 550 may be presented with information about what will be managedand/or queried by the server. The configuration profile may be sent orprovided to the mobile device 550 is a variety of methods, e.g. email,text message, web browser link, physical loading via a connection to themobile device 550, and the like. Also, the configuration profile mayinclude software configured to operate on the mobile device 550 tocoordinate and provide the MDM functionality.

The user (or an IT administrator) installs the profile to opt the mobiledevice 550 into being managed by the MDM server 804 or the cloud node502. The mobile device 550 is enrolled as the profile is being installed(step 816). The server 804/cloud node 502 validates the mobile device550 and allows access. The push notification server 802 sends a pushnotification prompting the mobile device 550 to check in for tasks,queries, etc. (step 818). Finally, the mobile device 550 connectsdirectly to the MDM server 804 or the cloud node 502, such as over HTTPS(step 820). The MDM server 804 or the cloud node 502 is configured tooperate with the installed profile on the mobile device 550.Specifically, the MDM server 804 or the cloud node 502 may send commandsto or request information from the mobile device 550. The exemplarycommands may include the various functions described herein withreference to the provisioning methods 600, 700 or any other MDM relatedfunctions. The platform specific MDM configuration 800 is describedherein using the push notification server 802 and the MDM server 802 orthe cloud node 502. Generally, the platform specific MDM configuration800 uses other MDM platform specific clients that need to be installedon the mobile device and use various APIs to get configuration updatesand report status to the MDM server 804 or the cloud node 502.

Referring to FIGS. 9-14, in various exemplary embodiments, graphicaluser interfaces (GUI) illustrate screen shots of an MDM provisioningplatform. As described herein, the cloud system 500 or the distributedsecurity system 100 may provide a cloud based MDM system and method.Since the cloud nodes 502 and/or the processing nodes 110 act as proxiesfor the mobile device 550, they can log all traffic and concurrentlyprovide MDM functionality. Each of the cloud system 500 or thedistributed security system 100 has a management system. For example,the distributed security system 100 has the user interface front-end130. The cloud system 500 may have a similar function. Specifically, themanagement system provides an administrator with a consolidated view formanaging and provisioning the cloud system 500 and the distributedsecurity system 100. In an exemplary embodiment, the cloud based MDMsystem and method may include an integrated dashboard such as throughthe management system, the user interface front-end 130, a web serverassociated with the cloud nodes 502, and the like. This integrateddashboard may be utilized by the administrator to define configurations,policy, security, provisioning, etc. of the mobile devices 550.Furthermore, the integrated dashboard may provide transaction logs,alerts, reports, etc. related to MDM of the mobile devices 550.

FIGS. 9-14 illustrate exemplary screen shots of the integrateddashboard. FIG. 9 is a GUI representing general settings, such as devicename, a setting for allowing non-provisionable devices, and a settingfor refresh interval. For example, the GUIs are examples using MicrosoftExchange ActiveSync. The refresh interval is a setting to determine howoften the mobile device 550 communicates with the MDM server 804 or thecloud node 502 to receive updates. FIG. 10 is a GUI representingpassword related settings for the mobile device 550. Here, theadministrator can make various settings as described herein related tothe password of the mobile device 550. FIG. 11 is a GUI representingsynchronization settings. Here, the administrator can make varioussettings for synchronizing the mobile device 550 to an Exchange serveror some other mail server. FIG. 12 is a GUI representing devicesettings. Here, the administrator can define policy related to themobile device 550 usage of various items, e.g. camera, etc. FIG. 13 is aGUI representing device application settings. Here, the administratorcan define usage policy related to the mobile device 550. Finally, FIG.14 is a GUI representing other settings. In an exemplary embodiment, theother settings may include a list of allowed applications/blockedapplications. The administrator may prohibit or allow the use ofspecifically enumerated applications.

Referring to FIGS. 15 and 16, in various exemplary embodiments, GUIsillustrate screen shots of reporting and graphing associated with thecloud based MDM system and method. FIG. 15 illustrates an exemplary listof mobile device 550 under the management of the cloud based MDM systemand method. This list may include various attributes, user ID, username, device type, etc., and may be sorted by any column. The list mayallow sort, search, and ability to apply pre-defined policy profiles toselected users. Further, an administrator may click on a particular userto drill down into more details. The list may provide a convenientmethod of applying the policy to multiple mobile devices 550simultaneously. Further, the cloud based MDM system and methodcontemplate location based policies—even on Apple devices. Here, themobile devices 550 may be set for different policies based on whichcloud node 502 they are connected through. This may be provisionedthrough the list or through another GUI. FIG. 16 illustrates a graphassociated with the cloud based MDM system and method. That is, theintegrated dashboard may include a reporting tab which provides theadministrator with an ability to do reporting, tracking, etc. In FIG.16, a pie chart illustrates a division of types of mobile devices 550associated with the cloud based MDM system and method. The cloud basedMDM system and method can provide numerous reports, such as number ofdevices by platform that have checked in over a period of time, numberof missing devices by platform that have not checked in, etc. Further,the cloud based MDM system and method contemplates an ability to drilldown to gather further details on devices, history, etc.

As described herein, the cloud based MDM system and method contemplateMDM management through the cloud thereby reducing or eliminating theneed for external equipment, software, etc. to provide MDM. With thecloud, policies may be dynamic, adaptable based on individual userbehavior, aggregate user behavior, user location, etc. Specifically, thecloud enables IT administrators to see a global view. For example, if anew mobile application is introduced that has a perilous effect on theenterprise, the administrator can block this mobile application acrossall mobile devices 550 in a single step. The cloud based MDM furtherprovides flexibility to IT administrators allowing prevention of dataleakage across mobile devices, and the like. The cloud can protectdifferent mobile devices across different networks in a singleintegrated fashion. The cloud is pervasive and up-to-date with respectto security threats. The cloud by nature is distributed enabling accessacross the enterprise, i.e. HQ as well as road warrior employees. Thecloud provides a quick rollout, low maintenance, and low cost ofownership for the enterprise. Finally, the cloud is inherently resilientand scalable.

Referring to FIGS. 17A and 17B, in an exemplary embodiment, a network1700 illustrates an exemplary implementation of the present inventionwith one or more mobile devices 400 communicatively coupled to anexternal network 1710 (e.g., the Internet) via the distributed securitysystem 100, the cloud system 500, or the like. In particular, the mobiledevices 400 may include any of the aforementioned mobile devicesdescribed herein. The distributed security system 100, the cloud system500, or any other cloud-based system is configured to provide real-time,continuous inspection of mobile data transactions while not impactingperformance. Further, the distributed security system 100, the cloudsystem 500, etc. advantageously is platform-independent allowing themobile devices 400 to be any type of device, platform, operating system,etc. while providing a consistent level of protection. In an exemplaryembodiment, the mobile devices 400 are communicatively coupled to thedistributed security system 100, such as, for example, via theprocessing nodes 110 or to the cloud system 500 via the cloud nodes 502.Note, the mobile devices 400 may access the distributed security system100, the cloud system 500, etc. via a service provider's wirelessnetwork, via a Wi-Fi hotspot, via a wired connection, etc. Each of themobile devices 400 may include an application, configuration settings,operating system settings, and combinations thereof that configured themobile device 400 to communicate through to the distributed securitysystem 100, the cloud system 500, etc.

In FIG. 17A, the distributed security system 100, the cloud system 500,etc. is configured to act as a gatekeeper with respect to trafficforwarded from the mobile device 400 to the network 1710 and for trafficforward from the network 1710 to the mobile device 400. In particular,the system 100, 500 is configured to enforce policy guidelines withrespect to traffic from the mobile device 400 to the network 910. Asdescribed herein, policy refers to a set of use guidelines associatedwith the mobile device 400. Exemplary policies may include, but notlimited to, data usage, time-of-day, location (work vs. off-site), usingsocial networking sites, operating a particular application, black listof websites, and the like. The system 100, 500 may enforce policy in avariety of ways including blocking non-compliant traffic and displayinga notification on the mobile device 400, alerting an administrator 1720,and the like. For example, the administrator 1720 of the system 100, 500may interact with the system 100, 500 to define policy guidelines aswell as to receive reports from the system 100, 500 associated with themobile devices 400. Concurrent with the policy enforcement, the system100, 500 may also inspect content from the network 1710 for maliciouscontent (e.g., malware, spyware, viruses, email spam, etc.) and blockingsuch content from the mobile device 400.

Thus, the implementation of the network 1700 provides a cloud-basedsecurity system to the mobile devices 400 that is a user, location, andplatform independent. There is no requirement for external software onthe mobile device 400 other than configuration settings that instructthe mobile device 400 to communicate data through the system 100, 500.In an exemplary embodiment, the mobile device 400 is configured tocommunicate solely data traffic through the system 100, 500 while voicetraffic is handled directly with an end service provider. The network1700 offers a seamless solution that works independent of platform,requires no updates on the mobile device, filtering and policyenforcement is performed in the cloud, etc. In another exemplaryembodiment, the network 1700 may provide IT administrators an ability tomonitor and prevent specific applications on the mobile devices 400.This may prevent unacceptable or risky applications.

The network 1700 enforces policy in the cloud, not on the mobile device400. This means all network content is scanned, both browser andapplication generated web traffic, to ensure that malicious content isblocked in the cloud—long before it reaches the mobile device 400, orthe corporate network. Unlike other mobile security solutions thatrequire platform-specific applications to be installed on every device,the present invention works seamlessly across mobile platforms,including iPhones, iPads, and Android devices, for example.Advantageously, the present invention requires no signature updates onthe mobile device 400 and provides real-time inspection in the cloud forevery web or data transaction, regardless of whether it came from abrowser or from an application installed on the device. Further, thepresent invention runs in the cloud and has no impact on the mobiledevice's performance, battery life, or processing resources. Also, thesystem 100, 500 may provide real-time logs and reports for any user,from any location, on any device, at any time.

FIG. 17B illustrates a network diagram of the network 1700 showing themobile devices 400 connected to the system 100, 500 via a serviceprovider network 1730. The system 100, 500 is an intermediary betweenthe mobile devices 400 and the network 1710, e.g. the Internet. Theservice provider network 1730 may include any network by which themobile devices 400 obtain connectivity including, for example, awireless carrier (3G, 4G, LTE, WIMAX, etc.), a wireless hotspot (IEEE802.11), an ad hoc connection, a wired connection, etc. In an exemplaryembodiment, the mobile devices 400 may connect over the service providernetwork 1730 using a secure VPN tunnel to the system 100, 500. Inanother exemplary embodiment, the mobile devices 400 may connect overthe service provider network 1730 using a HyperText Transfer Protocol(HTTP) proxy. The network administrator 1720 is connected to the system100, 500 via the service provider network 1730, via the network 1710,directly, and the like.

Referring to FIG. 18, in an exemplary embodiment, a flow chartillustrates a mobile device use method 1800 for using a cloud-basedsecurity system with a mobile device. The method 1800 may, for example,be implemented in the network 900 such as through the mobile device 400and the system 100, 500 (or alternatively any cloud-based system). Thesteps shown in FIG. 18 are each processes that can be executedindependently and concurrently as appropriate. First, an enterprise orthe like pushes a mobile profile and/or application on an end user'smobile device (step 1802). In an exemplary embodiment, the push includespushing configuration settings on the mobile device such that datatraffic flows through the cloud-based security system. This may includean HTTP Proxy, a VPN between the mobile device and the cloud-basedsystem, from devices in a carrier or service provider's network to thecloud-based system, from a Wi-Fi network to the cloud-based system, etc.For example, a specific operating system associated with the mobiledevice 400 may natively support such configurations. Alternatively, anapplication may be pushed onto the mobile device 400 to provide such aconnection to the cloud-based security system. The mobile profile and/orthe application is installed on the end user's mobile device (step1804). Once installed, the mobile device is configured to connect to anetwork using the mobile profile and/or the application (step 1806).Here, the mobile device is configured such that data communication(e.g., web, email, etc.) is through the cloud-based security system. Thecloud-based security system is configured to provide content inspectionand policy enforcement (step 1808).

Referring to FIG. 19, in an exemplary embodiment, a flow chartillustrates a mobile application classification method 1900 forclassifying applications associated with mobile devices. The method 1900may, for example, be implemented in the network 1700 such as through themobile device 400 and the system 100, 500 (or alternatively anycloud-based system) or on a device, such as the server 300communicatively coupled to the network 1700. The steps shown in FIG. 19are each processes that can be executed independently and concurrentlyas appropriate. The method 1900 may be utilized for classifyingapplications based on their security and privacy profile and leveragingthe associated data to provide protection and policy enforcement forapplications by leveraging the cloud. First, a plurality of applicationsfor mobile devices is analyzed for various attributes (step 1902). Theapplications may include mobile applications on Apple's App Store,Google's Android Market, and the like. Exemplary attributes may includeapplication creator, category, user-agent strings used by theapplication to communicate over the network, security attributes,privacy attributes, and the like. The purpose of the method 1900 is toclassify each application with an associated score defining risk. Forexample, in one exemplary embodiment, the method 1900 may determine asecurity score and a privacy score for each of the plurality ofapplications (step 1904). These scores may take any form (numerical,alphabetical, etc.). For example, the scores may be based on a numericalrange, e.g. 1-10 where 1 is very secure and 10 is very insecure. Thesescores may define a mobile Application Security Rating (ASR).

In an exemplary embodiment, the security score may be computed basedon 1) a security analysis done for the application, 2) applicationpermissions which determine what the application is capable ofaccessing, 3) reputation of the vendor that created the application, 4)feedback from users, 5) real-time analysis of app behavior in the cloud,and 6) combinations thereof. In an exemplary embodiment, the privacyscore may be based on 1) a privacy analysis done for the application, 2)feedback from users of the application around security, 3) real-timeanalysis of app behavior in the cloud, and 4) combinations thereof. Withthis data, a database may be created with the plurality of applicationsand their associated scores and attributes (step 1906). For example, thedatabase may be at a server 300 in the cloud-based system, such as at aprocessing node 110, at an authority node 120, the cloud node 502, orcombinations thereof. This database may be continually or periodicallyupdated (step 1908). For example, the database may be updated as newapplications emerge, as new ratings are determined based on thecloud-based system, etc. Further, the method 1900 is configured toprovide the scores and the attributes on demand as required by thecloud-based system (step 1910). For example, the cloud-based system mayutilize this data in a policy enforcement step, i.e. is a particularapplication requested by a mobile device allowed per policy, does itmeet a minimum threshold for security and/or privacy, will thisapplication interfere with an enterprise network, etc.

Referring to FIG. 20, in an exemplary embodiment, a flow chartillustrates a mobile device security method 2000 using a cloud-basedsecurity system with a mobile device. The method 2000 may, for example,be implemented by a cloud-based system such as in the network 1700through the mobile device 400 and the system 100, 500 (or alternativelyany cloud-based system). The steps shown in FIG. 20 are each processesthat can be executed independently and concurrently as appropriate. Themethod 2000 assumes the mobile device is configured to operate with thecloud-based system (such as through the method 1800). A cloud-basedsystem receives data from a mobile device (step 2002). As describedherein, the mobile device is configured to communicate data trafficthrough the cloud-based security system. The data may include Webtraffic and the like. In an exemplary embodiment, the data may beforwarded to the cloud-based system through a variety of mechanisms suchas, for example, a Hypertext Transfer Protocol (HTTP) Proxy, a VPNbetween the mobile device and the cloud-based system, from devices in acarrier or service provider's network to the cloud-based system, from aWi-Fi network to the cloud-based system, etc. For example, related to acarrier or service provider's network, a user of the mobile device mayaccess a wireless network, e.g. a 3G/4G network from any of AT&T,Verizon, Sprint, T-Mobile, etc. In this embodiment, the cloud-basedsystem may be configured to receive direct data from the mobile devicewithout requiring an HTTP proxy, VPN, etc.

The cloud-based system is configured to analyze data from the mobiledevice to apply predefined policy (step 2004). As described herein, thepolicy may be broadly defined as any acceptable-use activity defined byan IT administrator, etc. For example, the acceptable-use activity mayinclude blocking use and/or installation of applications based on themobile Application Security Rating, preventing access to blacklisted Websites, data use during specified times (e.g., at work), and the like.The administrator can define policies that block applications based onApplication Security Rating, category, vendor, etc. In another exemplaryembodiment, the data may include a Web request and the cloud-basedsystem may implement the Web Risk Index described herein to determinewhether or not to forward such request. Policies may be defined for acompany, group or user. Appropriate application policies are enforced inline. For example, applications that are deemed malicious or violatingthe policy can be prevented from being downloaded by the secure webgateway. That is, if the cloud-based system deems the data from themobile device violates a policy (step 2006), the data may be blocked(step 2008). In an exemplary embodiment, the data may be blocked, and amessage may be provided to the mobile device notifying a user as such.

If the data does not violate a policy (step 2006), the cloud-basedsystem may forward the data to an external network (step 2010). Forexample, the cloud-based system may forward the data to the Internetincluding a designated Web site. Subsequently, the cloud-base system mayreceive a data response from the network for the mobile device based onthe initially forwarded data (step 2012). Upon receipt of the dataresponse, the cloud-based system is configured to inspect the content ofthe data response (step 2014). Here, the cloud-based system isconfigured to provide real-time traffic analysis and enforcement in thecloud. As described herein, the system 100, 500 may provide a securegateway to view all data transactions in real-time and provide contentinspection with respect to malicious content including, but not limitedto, viruses, spyware, malware, Trojans, botnets, spam email, phishingcontent, inappropriate content with respect to policy, blacklistedcontent, and the like. In particular, the cloud-based system isconfigured to determine if the content is valid and/or capable of beingforwarded to the mobile device (step 2016). If the cloud-based systemdetermines for some reason (e.g., malicious content, unapprovedapplication, risky content from a security or privacy perspective,policy violation, etc.), the cloud-based system may block the data fromthe mobile device (step 2008) and potentially notify the user and/or theIT administrator. Alternatively, if the data response is clean and notin violation of any defined policy, the data response from the networkmay be forwarded to the mobile device by the cloud-based system (step2018).

Referring to FIG. 21, in an exemplary embodiment, a flowchart and screenshots illustrate an exemplary operation 2100 of IPsec VPN with cloudbased mobile device security and policy systems and methods. InternetProtocol Security (IPsec) is a protocol suite for securing InternetProtocol (IP) communications by authenticating and encrypting each IPpacket of a communication session. IPsec also includes protocols forestablishing mutual authentication between agents at the beginning ofthe session and negotiation of cryptographic keys to be used during thesession. In an exemplary embodiment, the mobile device 400 may use anIPsec VPN to communicate to the system 100, 500. First, an administratorpushes a mobile configuration profile on/to a mobile device (step 2101).In an exemplary embodiment, this push may include a two-dimensional barcode that is input into the mobile device via a scanner, a camera, etc.A user installs the mobile profile on the mobile device (step 2102). Forexample, following the configuration push, the user may be presentedwith a screen for the user to confirm or initiate installation. Themobile device may automatically connect to the installed IPsec VPN ondemand (step 2103). For example, the user may initiate a connection viaa screen to connect to the IPsec VPN. Alternatively, the IPsec VPN maybe automatically always on. Finally, security and policymanagement/enforcement is performed in the cloud (step 2104). Forexample, a screen shot illustrates a user screen when the cloud detectsa virus. In lieu of downloading the virus to the mobile device, thecloud blocks the content and provides relevant details to the user.

Referring to FIG. 22, in an exemplary embodiment, a flowchart and screenshots illustrate an exemplary operation 2200 of Junos Pulse SecureSocket Layer (SSL) with cloud based mobile device security and policysystems and methods. Junos Pulse (available from Juniper Networks, Inc.)for iOS enables secure connectivity over SSL VPN to corporateapplications and data from anywhere, at any time. Using Junos Pulse, auser can connect securely to a corporate Juniper Networks SA Series SSLVPN gateway and gain instant access to business applications andnetworked data anywhere. In an exemplary embodiment, the mobile device400 may use a Junos Pulse SSL VPN to communicate to the system 100, 500.First, an administrator pushes a mobile configuration profile on/to amobile device (step 2201). In an exemplary embodiment, this push mayinclude a two-dimensional bar code that is input into the mobile devicevia a scanner, a camera, etc. A user installs the mobile profile on themobile device (step 2202). For example, following the configurationpush, the user may be presented with a screen for the user to confirm orinitiate installation. The mobile device may automatically connect tothe installed Junos Pulse SSL VPN on demand (step 2103). For example,the user may initiate a connection via a screen to connect to the JunosPulse SSL VPN. Alternatively, the Junos Pulse SSL VPN may beautomatically always on. Finally, security and policymanagement/enforcement is performed in the cloud (step 2104). Forexample, a screen shot illustrates a user screen when the cloud detectsa virus. In lieu of downloading the virus to the mobile device, thecloud blocks the content and provides relevant details to the user.

Referring to FIGS. 23-26, in various exemplary embodiments, screenshotsillustrate security and policy enforcement in the cloud on a mobiledevice. For example, the screen shots may be on the mobile device 400being used with the system 100, 500. In each of FIGS. 23-26, the mobiledevice with the screen shots is connected to a cloud based securitysystem. In FIG. 23, the mobile device communicates with an exemplarysite with a Jailbreak application. Jailbreaking leverages knownvulnerabilities of a mobile device to unlock the device. At its core,jailbreaking a mobile device gives access to its root filesystem,allowing modification and installing third-party software components.This gives the user more control over the device and may enable featuresthat were previously unavailable. In many cases, also jailbreaking voidsthe device's warranty. Upon initiating a download of the Jailbreak, thecloud based security system blocks the content and informs the user thata virus was detected in the web page or file that the user sought todownload. For example, the screenshot may include information related tothe blocked content (e.g., location), a category of the content (e.g.,trojan), the activity taken (e.g., blocked), and contact information forthe defined policy and IT support.

FIG. 24 illustrates two blocked screen shots related to defined policy.For example, a network administrator may define acceptable use andcontent for its users. This may include blocking pornographic sites,gambling sites, social media sites, or any other content. FIG. 25illustrates the mobile device communicating with an exemplary site withCross-site scripting (XSS). Cross-site scripting (XSS) is the mostcommon web application vulnerability encountered today. XSSvulnerabilities can lead to a variety of attacks such as cookie theft,overwriting page content or screen shaping. Cross-site scripting (XSS)is a type of computer security vulnerability typically found in webapplications that enable attackers to inject client-side script into webpages viewed by other users. A cross-site scripting vulnerability may beused by attackers to bypass access controls such as the same originpolicy. Upon initiating a download of the XSS (i.e., selecting the StealMy Cookie! Button), the cloud based security system blocks the contentand informs the user of a Security Notification and that the site orfile was blocked. For example, the screenshot may include informationrelated to the blocked content (e.g., location), a category of thecontent (e.g., possible cookie theft), the activity taken (e.g.,blocked), and contact information for the defined policy and IT support.FIG. 26 illustrates the mobile device communicating with an exemplaryphishing site. Phishing attacks can be even more effective againstmobile devices. The attacks tend to be short-lived and exploit the factthat mobile devices are always connected and have small screens withtouch interfaces. Upon initiating browsing to the phishing site, thecloud based security system blocks the content and informs the user of aSecurity Notification and that the site or file was blocked. Forexample, the screenshot may include information related to the blockedcontent (e.g., location), a category of the content (e.g., possiblephishing site), the activity taken (e.g., blocked), and contactinformation for the defined policy and IT support.

Referring to FIG. 27, in an exemplary embodiment, a screen shotillustrates a user interface for a network administrator of a cloudbased security system. For example, the screenshot may be associatedwith the system 100, 500 and accessed via a network connection to thesystem 100, 500. Through the user interface, the network administratormay define policy and security for individual users, groups of users,the entire population of users, etc. as well as manage policy andsecurity. The screen shot of FIG. 27 shows an example of a userinterface where the network administrator may view, e.g. via variousfilters, security and policy events in the cloud based security systemover a defined period (e.g., the last three hours).

Although the present invention has been illustrated and described hereinwith reference to preferred embodiments and specific examples thereof,it will be readily apparent to those of ordinary skill in the art thatother embodiments and examples may perform similar functions and/orachieve like results. All such equivalent embodiments and examples arewithin the spirit and scope of the present invention and are intended tobe covered by the following claims.

What is claimed is:
 1. A mobile device security and policy enforcementmethod implemented by a node in a cloud based system, comprising:subsequent to communicatively coupling a mobile device to the node,monitoring data between the mobile device and an external network;performing one or more of (i) enforcing policy relative to the data,wherein the policy is associated with a user of the mobile device and(ii) inspecting the data for malicious content therein; allowing thedata responsive to the data complying with the policy and/or containingno malicious content; and blocking the data in the node responsive tothe data not complying with the policy and/or containing maliciouscontent.
 2. The mobile device security and policy enforcement method ofclaim 1, wherein the monitoring, the enforcing, the inspecting, theallowing, and the blocking is performed by the node without aplatform-specific app on the mobile device.
 3. The mobile devicesecurity and policy enforcement method of claim 1, wherein the maliciouscontent comprises one or more of viruses, spyware, malware, Trojans,botnets, spam email, phishing content, and blacklisted content.
 4. Themobile device security and policy enforcement method of claim 1, whereinthe policy comprises one or more of inappropriate content, data leakage,data usage limits, time-of-day usage limits, location, operation of aparticular application, and black lists of websites.
 5. The mobiledevice security and policy enforcement method of claim 1, wherein thepolicy comprises preventing installation of a particular application onthe mobile device.
 6. The mobile device security and policy enforcementmethod of claim 5, wherein the particular application is blocked for oneor more of failing to meet a minimum threshold for security and/orprivacy and interfering with an enterprise network associated with theuser.
 7. The mobile device security and policy enforcement method ofclaim 1, further comprising: receiving an update to the policy for theuser or for a group of users comprising the users; and performing theenforcing with the updated policy.
 8. The mobile device security andpolicy enforcement method of claim 1, further comprising: receiving anupdate related to the malicious content from another node in the cloudbased system; and performing the inspecting the data with the update. 9.The mobile device security and policy enforcement method of claim 1,wherein the node forms an association with the mobile device.
 10. Amobile device security and policy enforcement system, comprising: anetwork interface communicatively coupled to a processor; and memorystoring instructions that, when executed, cause the processor to:subsequent to communicatively coupling to a mobile device, monitor databetween the mobile device and an external network; perform one or moreof (i) enforce policy relative to the data, wherein the policy isassociated with a user of the mobile device, and (ii) inspect the datafor malicious content therein; allow the data responsive to the datacomplying with the policy and/or containing no malicious content; andblock the data in the node responsive to the data not complying with thepolicy and/or containing malicious content.
 11. The mobile devicesecurity and policy enforcement system of claim 10, wherein the mobiledevice does not utilize a platform-specific app for mobile devicesecurity and policy enforcement.
 12. The mobile device security andpolicy enforcement system of claim 10, wherein the malicious contentcomprises one or more of viruses, spyware, malware, Trojans, botnets,spam email, phishing content, and blacklisted content.
 13. The mobiledevice security and policy enforcement system of claim 10, wherein thepolicy comprises one or more of inappropriate content, data leakage,data usage limits, time-of-day usage limits, location, operation of aparticular application, and black lists of websites.
 14. The mobiledevice security and policy enforcement system of claim 10, wherein thepolicy comprises preventing installation of a particular application onthe mobile device.
 15. The mobile device security and policy enforcementsystem of claim 14, wherein the particular application is blocked forone or more of failing to meet a minimum threshold for security and/orprivacy and interfering with an enterprise network associated with theuser.
 16. The mobile device security and policy enforcement system ofclaim 10, wherein the memory storing instructions that, when executed,further cause the processor to: receive an update to the policy for theuser or for a group of users comprising the users; and enforce thepolicy with the updated policy.
 17. The mobile device security andpolicy enforcement system of claim 10, wherein the memory storinginstructions that, when executed, further cause the processor to:receive an update related to the malicious content from another node inthe cloud based system; and inspect the data with the update.
 18. Themobile device security and policy enforcement system of claim 10,wherein the node forms an association with the mobile device.
 19. Amobile device, comprising: a network interface communicatively coupledto a processor; and memory storing instructions that, when executed,cause the processor to: subsequent to communicatively coupling to a nodein a mobile device security and policy enforcement system, transmit datato an external network through the node, wherein responsive to the dataone or more of (i) complying with policy associated with a user of themobile device based on enforcement by the node and (ii) containing nomalicious data therein based on inspection by the node, the node isconfigured to allow the data; responsive to responsive data from theexternal network one or more of (i) complying with the policy based onenforcement by the node and (ii) containing no malicious content thereinbased on inspection by the node, receive the responsive data, from thenode; and responsive to any of the data not complying with the policy,responsive to the data containing malicious data therein, responsive tothe responsive data from the external network not complying with thepolicy, or responsive to the responsive data containing maliciouscontent therein, receive a notification from the node.
 20. The mobiledevice of claim 19, wherein the mobile device does not execute aplatform-specific application related to policy enforcement and datainspection by the node.